Skip to content

Conversation

@damonfeldman
Copy link
Contributor

It appears the logRequest flag changed to logDQLRequest on or about v23.0 or v23.1.

Updating docs.

It appears the logRequest flag changed to logDQLRequest on or about v23.0 or v23.1.

Updating docs.
@netlify
Copy link

netlify bot commented Sep 5, 2023

Deploy Preview for dgraph-docs-repo ready!

Name Link
🔨 Latest commit d3abf64
🔍 Latest deploy log https://app.netlify.com/sites/dgraph-docs-repo/deploys/64f69a3f1404030008189ef1
😎 Deploy Preview https://deploy-preview-642--dgraph-docs-repo.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@Rajakavitha1 Rajakavitha1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Rajakavitha1 Rajakavitha1 merged commit 0b1d592 into release/v23.0 Sep 5, 2023
@Rajakavitha1 Rajakavitha1 deleted the damonfeldman-logDQLRequest-param branch September 5, 2023 04:30
rderbier pushed a commit that referenced this pull request Sep 14, 2023
It appears the logRequest flag changed to logDQLRequest on or about
v23.0 or v23.1.

Updating docs.


<!--
Title: Please use the following format for your PR title: topic(area):
details
- The "topic" should be one of the following: Docs, Nav or Chore
- The "area" is the feature (i.e., "GraphQL"), area of the docs (i.e.,
"Deployment"), or "Other" (for typo fixes and other bug-fix PRs).
Sample Titles:
  Docs(GraphQL): Document the @deprecated annotation
  Chore(Other): cherry-pick updates from main to release/v20.11

Description: Please include the following in your PR description:
1. A brief, clear description of the change.
2. Link to any related PRs or discuss.dgraph.io posts.
3. If this PR corresponds to a JIRA issue, include "Fixes DOC-###" in
the PR description.
3. If this is a breaking change, please put "[Breaking]" in the title.
In the description, please put a note with exactly who these changes are
breaking for.
4. If you are creating a PR in `main` and you know it needs to be
cherry-picked to a release branch, please mention that in your PR
description (for example: "cherry-pick to v20.07"). Cherry-pick PRs
should reference the original PR.

Note: Create and edit docs in the `main` branch when you can, so that we
only cherry-pick out of `main`, not into `main`.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants